Skip to content

Release ti ticura 0.1.0 - #19280

Merged
kcreddy merged 39 commits into
elastic:mainfrom
ticura:release-ti_ticura-0.3.1
Jun 26, 2026
Merged

kcreddy merged 39 commits into
elastic:mainfrom
ticura:release-ti_ticura-0.3.1

Conversation

@eduardenes-ticura

@eduardenes-ticura eduardenes-ticura commented May 29, 2026 •

Copy link
Copy Markdown
Contributor

Initial release of the ti_ticura integration (version 0.1.0)

  • WHAT: Added the ti_ticura integration with all required assets, including pipelines, data streams, rules, searches, dashboards, and fields. This is the first release of this integration.
  • WHY: To make the ti_ticura integration available to users via the Elastic Package Registry.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

  • Verify CI passes and all package assets are valid

How to test this PR locally

  1. Run elastic-package check in the integration directory
  2. Run elastic-package stack up -d and elastic-package install
  3. Verify that data streams, pipelines, and dashboards work as expected after using a ticura ecs feed for integration.

How to verify end-to-end against the live Ticura API:

  1. Create a free trial account at https://app.ticura.io/ , generate a feed with ECS output format and copy the API key.
  2. In Kibana, Management → Integrations → Ticura → Add, configure api_token, leave interval at 15 m.
  3. Verify indicators land in logs-ti_ticura.ecs-* within one poll cycle.
  4. Open [Ticura] Overview dashboard — should show the indicators.
  5. Open Security → Rules → Detection rules, filter by tag Ticura, confirm 5 rules are present and disabled.

Related issues

  • N/A for initial release

Screenshots

image

@eduardenes-ticura
eduardenes-ticura requested a review from a team as a code owner May 29, 2026 07:05
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

Reviewers

Buildkite won't run for external contributors automatically; you need to add a comment:

  • /test : will kick off a build in Buildkite.

NOTE: https://github.com/elastic/integrations/blob/main/.buildkite/pull-requests.json contains all those details.

@eduardenes-ticura

Copy link
Copy Markdown
Contributor Author

@efd6 @andrewkroh @jsoriano Hi team, I’d love to get your feedback when you have a chance.
Happy to make any changes if needed to get the release done.

@andrewkroh andrewkroh added documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. New Integration Issue or pull request for creating a new integration package. labels May 29, 2026
@kcreddy

kcreddy commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

/test

@kcreddy kcreddy added the Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] label Jun 4, 2026
@infra-vault-gh-plugin-prod

Copy link
Copy Markdown

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@github-actions

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Elastic Docs Style Checker (Vale)

Summary: 8 warnings, 3 suggestions found

⚠️ Warnings (8): Fix when the suggestion improves clarity or correctness.
File Line Rule Message
packages/ti_ticura/_dev/build/docs/README.md 5 Elastic.EndPuntuaction Don't end headings with punctuation.
packages/ti_ticura/_dev/build/docs/README.md 100 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/ti_ticura/_dev/build/docs/README.md 100 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/ti_ticura/_dev/build/docs/README.md 100 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/ti_ticura/_dev/build/docs/README.md 169 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/ti_ticura/_dev/build/docs/README.md 188 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/ti_ticura/_dev/build/docs/README.md 246 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'versus' instead of 'vs'.
packages/ti_ticura/_dev/build/docs/README.md 318 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
💡 Suggestions (3): Optional style improvements. Apply when helpful.
File Line Rule Message
packages/ti_ticura/_dev/build/docs/README.md 154 Elastic.Wordiness Consider using 'all' instead of 'All of '.
packages/ti_ticura/_dev/build/docs/README.md 377 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/ti_ticura/changelog.yml 1 Elastic.Versions Use 'later versions' instead of 'newer versions' when referring to versions.

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

Comment thread packages/ti_ticura/changelog.yml Resolved
Comment thread packages/ti_ticura/manifest.yml Resolved
Comment thread packages/ti_ticura/manifest.yml Resolved
@eduardenes-ticura

eduardenes-ticura commented Jun 8, 2026 •

Copy link
Copy Markdown
Contributor Author

@kcreddy Handled findings / comments. Please re-test.

@kcreddy

kcreddy commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

/test

Comment thread packages/ti_ticura/manifest.yml Resolved
@kcreddy

kcreddy commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

/test

@eduardenes-ticura

Copy link
Copy Markdown
Contributor Author

@kcreddy I had to remove outdated rules that caused failed pipeline. Please re-test

@kcreddy

kcreddy commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

/test

@eduardenes-ticura

Copy link
Copy Markdown
Contributor Author

@kcreddy got it. thank you for all the support. just removed the agentless code and doku.

@vera-review-bot

Copy link
Copy Markdown
Contributor

👀 I have started reviewing the PR

@kcreddy

kcreddy commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

/test

@kcreddy kcreddy left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add this section to your README as well?
Once you run elastic-package build this will be rendered inside docs/README with your mapped fields and sample_event.json. Integration docs will look like this: https://www.elastic.co/docs/reference/integrations/ti_threatconnect#logs-reference

@eduardenes-ticura

Copy link
Copy Markdown
Contributor Author

@kcreddy extended readme as requested and rebuild the sample json. lets see if we're good to go now.

@vera-review-bot

Copy link
Copy Markdown
Contributor

👀 I have started reviewing the PR

@kcreddy

kcreddy commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

/test

@vera-review-bot

Copy link
Copy Markdown
Contributor

👀 I have started reviewing the PR

@vera-review-bot

Copy link
Copy Markdown
Contributor

👀 I have started reviewing the PR

@vera-review-bot

Copy link
Copy Markdown
Contributor

Vera Review Bot

For the current commit state, I did not find any issues.


🤖 AI-Generated Review | Vera Review Bot | 📚 Knowledge base: integration-skills

⚠️ Automated review — verify suggestions before applying.

@eduardenes-ticura

Copy link
Copy Markdown
Contributor Author

@kcreddy anything else we could do to proceed here? :-)

@kcreddy

kcreddy commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

/test

@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

✅ All changelog entries have the correct PR link.

@vera-review-bot

Copy link
Copy Markdown
Contributor

👀 I have started reviewing the PR

@infra-vault-gh-plugin-prod

Copy link
Copy Markdown

💚 Build Succeeded

History

@vera-review-bot

Copy link
Copy Markdown
Contributor

Vera Review Bot

For the current commit state, I did not find any issues.


🤖 AI-Generated Review | Vera Review Bot | 📚 Knowledge base: integration-skills

⚠️ Automated review — verify suggestions before applying.

@kcreddy kcreddy left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. @eduardenes-ticura, thanks for much for the patience and addressing all the review comments.

@mergify

mergify Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

  • Queue this pull request

@kcreddy
kcreddy merged commit df03b65 into elastic:main Jun 26, 2026
12 checks passed
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

Package ti_ticura - 0.1.0 containing this change is available at https://epr.elastic.co/package/ti_ticura/0.1.0/

@andrewkroh andrewkroh added dashboard Relates to a Kibana dashboard bug, enhancement, or modification. Integration:ti_ticura Ticura (Partner supported) labels Jun 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dashboard Relates to a Kibana dashboard bug, enhancement, or modification. documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. Integration:ti_ticura Ticura (Partner supported) maintainer:Partner Partner supported integration New Integration Issue or pull request for creating a new integration package. Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants